[INFO] fetching crate soma-ctf 0.1.0-alpha...
[INFO] fixing soma-ctf-0.1.0-alpha against try#622891a4e29178280638a6b63a8908bde2c0c854+cargoflags=-Zfix-edition=end=2015,2024 for pr-157817-2
[INFO] extracting crate soma-ctf 0.1.0-alpha into /workspace/builds/worker-4-tc2/source
[INFO] started tweaking crates.io crate soma-ctf 0.1.0-alpha
[INFO] finished tweaking crates.io crate soma-ctf 0.1.0-alpha
[INFO] tweaked toml for crates.io crate soma-ctf 0.1.0-alpha written to /workspace/builds/worker-4-tc2/source/Cargo.toml
[INFO] validating manifest of crates.io crate soma-ctf 0.1.0-alpha on toolchain 622891a4e29178280638a6b63a8908bde2c0c854
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+622891a4e29178280638a6b63a8908bde2c0c854" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }`
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+622891a4e29178280638a6b63a8908bde2c0c854" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Updating crates.io index
[INFO] [stderr]      Locking 242 packages to latest compatible versions
[INFO] [stderr]       Adding bollard v0.2.1 (available: v0.21.0)
[INFO] [stderr]       Adding clap v2.32.0 (available: v2.34.0)
[INFO] [stderr]       Adding crossterm v0.6.0 (available: v0.29.0)
[INFO] [stderr]       Adding dirs v1.0.5 (available: v6.0.0)
[INFO] [stderr]       Adding futures v0.1.31 (available: v0.3.32)
[INFO] [stderr]       Adding generic-array v0.14.7 (available: v0.14.9)
[INFO] [stderr]       Adding git2 v0.8.0 (available: v0.21.0)
[INFO] [stderr]       Adding handlebars v1.1.0 (available: v6.4.1)
[INFO] [stderr]       Adding hyper v0.12.36 (available: v1.10.1)
[INFO] [stderr]       Adding path-slash v0.1.5 (available: v0.2.1)
[INFO] [stderr]       Adding remove_dir_all v0.5.3 (available: v1.0.0)
[INFO] [stderr]       Adding serde_cbor v0.9.0 (available: v0.11.2)
[INFO] [stderr]       Adding tokio v0.1.22 (available: v1.52.3)
[INFO] [stderr]       Adding toml v0.4.10 (available: v1.1.2+spec-1.1.0)
[INFO] [stderr]       Adding typetag v0.1.8 (available: v0.2.22)
[INFO] [stderr]       Adding url v1.7.2 (available: v2.5.8)
[INFO] [stderr]       Adding wasi v0.10.0+wasi-snapshot-preview1 (available: v0.10.2+wasi-snapshot-preview1)
[INFO] [stderr]       Adding whoami v0.4.1 (available: v2.1.2)
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+622891a4e29178280638a6b63a8908bde2c0c854" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc2/source:/opt/rustwide/workdir:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-4-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-m" "1610612736" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:3a6becf2bc8dde7f3fa57ede90e4f284e72d296796fc446bbb1e2c7cc0530151" "sleep" "infinity", kill_on_drop: false }`
[INFO] [stdout] d39ec109b3c5270d1d929f84117aff0ae0af8cb60e1318da9824fd07448c723c
[INFO] running `Command { std: "docker" "start" "d39ec109b3c5270d1d929f84117aff0ae0af8cb60e1318da9824fd07448c723c", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "exec" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-w" "/opt/rustwide/workdir" "--user" "0:0" "d39ec109b3c5270d1d929f84117aff0ae0af8cb60e1318da9824fd07448c723c" "/opt/rustwide/cargo-home/bin/cargo" "+622891a4e29178280638a6b63a8908bde2c0c854" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "d39ec109b3c5270d1d929f84117aff0ae0af8cb60e1318da9824fd07448c723c", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "exec" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=" "-e" "RUSTDOCFLAGS=" "-w" "/opt/rustwide/workdir" "--user" "0:0" "d39ec109b3c5270d1d929f84117aff0ae0af8cb60e1318da9824fd07448c723c" "/opt/rustwide/cargo-home/bin/cargo" "+622891a4e29178280638a6b63a8908bde2c0c854" "fix" "--allow-no-vcs" "--allow-dirty" "--frozen" "--all" "--all-targets" "--message-format=json" "-Zfix-edition=end=2015,2024", kill_on_drop: false }`
[INFO] [stderr] crater-edition-check: migrating to next edition
[INFO] [stderr]    Migrating Cargo.toml from 2018 edition to 2021
[INFO] [stderr] note: Switching to Edition 2021 will enable the use of the version 2 feature resolver in Cargo.
[INFO] [stderr] This may cause some dependencies to be built with fewer features enabled than previously.
[INFO] [stderr] More information about the resolver changes may be found at https://doc.rust-lang.org/nightly/edition-guide/rust-2021/default-cargo-resolver.html
[INFO] [stderr] When building the following dependencies, the given features will no longer be used:
[INFO] [stderr] 
[INFO] [stderr]   syn v2.0.118 (as host dependency) removed features: extra-traits, visit, visit-mut
[INFO] [stderr] 
[INFO] [stderr]    Compiling crossbeam-utils v0.7.2
[INFO] [stderr]    Compiling memoffset v0.5.6
[INFO] [stderr]    Compiling crossbeam-epoch v0.8.2
[INFO] [stderr]     Checking iovec v0.1.4
[INFO] [stderr]     Checking net2 v0.2.39
[INFO] [stderr]     Checking lock_api v0.3.4
[INFO] [stderr]     Checking tokio-sync v0.1.8
[INFO] [stderr]    Compiling libz-sys v1.1.29
[INFO] [stderr]    Compiling parking_lot_core v0.6.3
[INFO] [stderr]    Compiling parking_lot v0.9.0
[INFO] [stderr]     Checking termios v0.3.3
[INFO] [stderr]    Compiling indexmap v1.9.3
[INFO] [stderr]    Compiling hyper v0.12.36
[INFO] [stderr]    Compiling libssh2-sys v0.2.23
[INFO] [stderr]    Compiling curl-sys v0.4.89+curl-8.20.0
[INFO] [stderr]    Compiling memchr v2.8.2
[INFO] [stderr]     Checking bytes v0.4.12
[INFO] [stderr]     Checking crossterm_utils v0.1.0
[INFO] [stderr]    Compiling ucd-trie v0.1.7
[INFO] [stderr]     Checking want v0.2.0
[INFO] [stderr]    Compiling openssl-macros v0.1.1
[INFO] [stderr]     Checking mio v0.6.23
[INFO] [stderr]     Checking futures-cpupool v0.1.8
[INFO] [stderr]     Checking time v0.1.45
[INFO] [stderr]     Checking idna v0.1.5
[INFO] [stderr]    Compiling libgit2-sys v0.7.11
[INFO] [stderr]    Compiling arrayvec v0.4.12
[INFO] [stderr]     Checking backtrace v0.3.76
[INFO] [stderr]     Checking crossterm_cursor v0.1.0
[INFO] [stderr]    Compiling ghost v0.1.21
[INFO] [stderr]    Compiling ctor v0.1.26
[INFO] [stderr]     Checking tokio-io v0.1.13
[INFO] [stderr]     Checking http v0.1.21
[INFO] [stderr]     Checking string v0.2.1
[INFO] [stderr]     Checking tokio-buf v0.1.1
[INFO] [stderr]     Checking openssl v0.10.81
[INFO] [stderr]     Checking hex v0.3.2
[INFO] [stderr]     Checking textwrap v0.10.0
[INFO] [stderr]     Checking pest v2.8.6
[INFO] [stderr]     Checking tokio-executor v0.1.10
[INFO] [stderr]     Checking crossbeam-queue v0.2.3
[INFO] [stderr]     Checking failure v0.1.8
[INFO] [stderr]     Checking tokio-codec v0.1.2
[INFO] [stderr]     Checking mio-uds v0.6.8
[INFO] [stderr]     Checking env_logger v0.6.2
[INFO] [stderr]     Checking tokio-reactor v0.1.12
[INFO] [stderr]     Checking tokio-timer v0.2.13
[INFO] [stderr]     Checking tokio-current-thread v0.1.7
[INFO] [stderr]     Checking crossterm_terminal v0.1.0
[INFO] [stderr]     Checking url v1.7.2
[INFO] [stderr]     Checking crossbeam-deque v0.7.4
[INFO] [stderr]     Checking xattr v1.6.1
[INFO] [stderr]     Checking crossterm_style v0.1.0
[INFO] [stderr]     Checking tokio-uds v0.2.7
[INFO] [stderr]     Checking tokio-threadpool v0.1.18
[INFO] [stderr]     Checking tokio-tcp v0.1.4
[INFO] [stderr]     Checking tokio-udp v0.1.6
[INFO] [stderr]     Checking crossterm_screen v0.1.0
[INFO] [stderr]     Checking crossterm_input v0.1.0
[INFO] [stderr]     Checking erased-serde v0.3.31
[INFO] [stderr]     Checking inventory v0.2.3
[INFO] [stderr]    Compiling typetag-impl v0.1.8
[INFO] [stderr]     Checking dirs v1.0.5
[INFO] [stderr]     Checking base64 v0.10.1
[INFO] [stderr]     Checking strsim v0.7.0
[INFO] [stderr]     Checking serde_cbor v0.9.0
[INFO] [stderr]     Checking crossterm v0.6.0
[INFO] [stderr]     Checking tempfile v3.27.0
[INFO] [stderr]     Checking tar v0.4.46
[INFO] [stderr]     Checking clap v2.32.0
[INFO] [stderr]     Checking toml v0.4.10
[INFO] [stderr]     Checking whoami v0.4.1
[INFO] [stderr]     Checking fs2 v0.4.3
[INFO] [stderr]     Checking path-slash v0.1.5
[INFO] [stderr]     Checking fs_extra v1.3.0
[INFO] [stderr]     Checking serde_test v1.0.177
[INFO] [stderr]     Checking typetag v0.1.8
[INFO] [stderr]     Checking tokio-fs v0.1.7
[INFO] [stderr]     Checking tokio v0.1.22
[INFO] [stderr]     Checking h2 v0.1.26
[INFO] [stderr]     Checking http-body v0.1.0
[INFO] [stderr]    Compiling pest_meta v2.8.6
[INFO] [stderr]    Compiling pest_generator v2.8.6
[INFO] [stderr]     Checking native-tls v0.2.18
[INFO] [stderr]    Compiling pest_derive v2.8.6
[INFO] [stderr]     Checking hyperlocal v0.6.0
[INFO] [stderr]     Checking hyper-tls v0.3.2
[INFO] [stderr]     Checking bollard v0.2.1
[INFO] [stderr]     Checking handlebars v1.1.0
[INFO] [stderr]     Checking git2 v0.8.0
[INFO] [stderr]     Checking soma-ctf v0.1.0-alpha (/opt/rustwide/workdir)
[INFO] [stderr]    Migrating src/lib.rs from 2018 edition to 2021
[INFO] [stderr]    Migrating tests/update.rs from 2018 edition to 2021
[INFO] [stderr]    Migrating tests/fetch.rs from 2018 edition to 2021
[INFO] [stderr]    Migrating tests/add_remove.rs from 2018 edition to 2021
[INFO] [stderr]    Migrating tests/run_stop.rs from 2018 edition to 2021
[INFO] [stderr]    Migrating src/bin/soma/main.rs from 2018 edition to 2021
[INFO] [stderr]    Migrating tests/location_to_backend.rs from 2018 edition to 2021
[INFO] [stderr]    Migrating tests/build_clean.rs from 2018 edition to 2021
[INFO] [stderr]     Finished `dev` profile [unoptimized + debuginfo] target(s) in 50.39s
[INFO] [stderr] crater-edition-check: soma-ctf v0.1.0-alpha (/opt/rustwide/workdir) updating edition from 2018 to 2021
[INFO] [stderr]     Checking serde v1.0.228
[INFO] [stderr]    Compiling openssl-macros v0.1.1
[INFO] [stderr]    Compiling pest_generator v2.8.6
[INFO] [stderr]    Compiling ghost v0.1.21
[INFO] [stderr]     Checking openssl v0.10.81
[INFO] [stderr]     Checking erased-serde v0.3.31
[INFO] [stderr]     Checking chrono v0.4.45
[INFO] [stderr]     Checking serde_cbor v0.9.0
[INFO] [stderr]     Checking toml v0.4.10
[INFO] [stderr]     Checking serde_test v1.0.177
[INFO] [stderr]    Compiling pest_derive v2.8.6
[INFO] [stderr]     Checking inventory v0.2.3
[INFO] [stderr]     Checking handlebars v1.1.0
[INFO] [stderr]     Checking typetag v0.1.8
[INFO] [stderr]     Checking native-tls v0.2.18
[INFO] [stderr]     Checking hyper-tls v0.3.2
[INFO] [stderr]     Checking bollard v0.2.1
[INFO] [stderr]     Checking soma-ctf v0.1.0-alpha (/opt/rustwide/workdir)
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]   --> src/lib.rs:73:20
[INFO] [stdout]    |
[INFO] [stdout] 73 |     pub fn printer(&self) -> RefMut<P> {
[INFO] [stdout]    |                    ^^^^^     ^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]    |                    |
[INFO] [stdout]    |                    the lifetime is elided here
[INFO] [stdout]    |
[INFO] [stdout]    = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout]    = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]    |
[INFO] [stdout] 73 |     pub fn printer(&self) -> RefMut<'_, P> {
[INFO] [stdout]    |                                     +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]  --> src/error.rs:3:17
[INFO] [stdout]   |
[INFO] [stdout] 3 | #[derive(Debug, Fail)]
[INFO] [stdout]   |                 ^---
[INFO] [stdout]   |                 |
[INFO] [stdout]   |                 `Fail` is not local
[INFO] [stdout]   |                 move the `impl` block outside of this constant `_DERIVE_failure_Fail_FOR_Error`
[INFO] [stdout] 4 | pub enum Error {
[INFO] [stdout]   |          ----- `Error` is not local
[INFO] [stdout]   |
[INFO] [stdout]   = note: the derive macro `Fail` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]   = note: the derive macro `Fail` may come from an old version of the `failure_derive` crate, try updating your dependency with `cargo update -p failure_derive`
[INFO] [stdout]   = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]   = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]   = note: `#[warn(non_local_definitions)]` on by default
[INFO] [stdout]   = note: this warning originates in the derive macro `Fail` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]  --> src/error.rs:3:17
[INFO] [stdout]   |
[INFO] [stdout] 3 | #[derive(Debug, Fail)]
[INFO] [stdout]   |                 ^---
[INFO] [stdout]   |                 |
[INFO] [stdout]   |                 `Display` is not local
[INFO] [stdout]   |                 move the `impl` block outside of this constant `_DERIVE_failure_core_fmt_Display_FOR_Error`
[INFO] [stdout] 4 | pub enum Error {
[INFO] [stdout]   |          ----- `Error` is not local
[INFO] [stdout]   |
[INFO] [stdout]   = note: the derive macro `Fail` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]   = note: the derive macro `Fail` may come from an old version of the `failure_derive` crate, try updating your dependency with `cargo update -p failure_derive`
[INFO] [stdout]   = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]   = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]   = note: this warning originates in the derive macro `Fail` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]   --> src/repository.rs:77:20
[INFO] [stdout]    |
[INFO] [stdout] 77 |     pub fn manager(&self) -> &'a RepositoryManager {
[INFO] [stdout]    |                    ^^^^^         ^^^^^^^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]    |                    |
[INFO] [stdout]    |                    the lifetime is elided here
[INFO] [stdout]    |
[INFO] [stdout]    = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]    |
[INFO] [stdout] 77 |     pub fn manager(&self) -> &'a RepositoryManager<'_> {
[INFO] [stdout]    |                                                   ++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/repository/backend.rs:12:1
[INFO] [stdout]    |
[INFO] [stdout] 12 | #[typetag::serde(tag = "type")]
[INFO] [stdout]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    | |
[INFO] [stdout]    | `Serialize` is not local
[INFO] [stdout]    | move the `impl` block outside of this constant `_Backend_registry`
[INFO] [stdout] 13 | pub trait Backend: BackendClone + Display {
[INFO] [stdout]    |           ------- `Backend` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the attribute macro `typetag::serde` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the attribute macro `typetag::serde` may come from an old version of the `typetag_impl` crate, try updating your dependency with `cargo update -p typetag_impl`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the attribute macro `typetag::serde` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/repository/backend.rs:12:1
[INFO] [stdout]    |
[INFO] [stdout] 12 | #[typetag::serde(tag = "type")]
[INFO] [stdout]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    | |
[INFO] [stdout]    | `Send` is not local
[INFO] [stdout]    | `Serialize` is not local
[INFO] [stdout]    | move the `impl` block outside of this constant `_Backend_registry`
[INFO] [stdout] 13 | pub trait Backend: BackendClone + Display {
[INFO] [stdout]    |           ------- `Backend` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the attribute macro `typetag::serde` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the attribute macro `typetag::serde` may come from an old version of the `typetag_impl` crate, try updating your dependency with `cargo update -p typetag_impl`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the attribute macro `typetag::serde` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/repository/backend.rs:12:1
[INFO] [stdout]    |
[INFO] [stdout] 12 | #[typetag::serde(tag = "type")]
[INFO] [stdout]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    | |
[INFO] [stdout]    | `Sync` is not local
[INFO] [stdout]    | `Serialize` is not local
[INFO] [stdout]    | move the `impl` block outside of this constant `_Backend_registry`
[INFO] [stdout] 13 | pub trait Backend: BackendClone + Display {
[INFO] [stdout]    |           ------- `Backend` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the attribute macro `typetag::serde` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the attribute macro `typetag::serde` may come from an old version of the `typetag_impl` crate, try updating your dependency with `cargo update -p typetag_impl`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the attribute macro `typetag::serde` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/repository/backend.rs:12:1
[INFO] [stdout]    |
[INFO] [stdout] 12 | #[typetag::serde(tag = "type")]
[INFO] [stdout]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    | |
[INFO] [stdout]    | `Send` is not local
[INFO] [stdout]    | `Sync` is not local
[INFO] [stdout]    | `Serialize` is not local
[INFO] [stdout]    | move the `impl` block outside of this constant `_Backend_registry`
[INFO] [stdout] 13 | pub trait Backend: BackendClone + Display {
[INFO] [stdout]    |           ------- `Backend` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the attribute macro `typetag::serde` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the attribute macro `typetag::serde` may come from an old version of the `typetag_impl` crate, try updating your dependency with `cargo update -p typetag_impl`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the attribute macro `typetag::serde` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/repository/backend.rs:12:1
[INFO] [stdout]    |
[INFO] [stdout] 12 | #[typetag::serde(tag = "type")]
[INFO] [stdout]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ move the `impl` block outside of this constant `_Backend_registry`
[INFO] [stdout] 13 | pub trait Backend: BackendClone + Display {
[INFO] [stdout]    |           ------- `Backend` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the attribute macro `typetag::serde` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the attribute macro `typetag::serde` may come from an old version of the `typetag_impl` crate, try updating your dependency with `cargo update -p typetag_impl`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the attribute macro `typetag::serde` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/repository/backend.rs:12:1
[INFO] [stdout]    |
[INFO] [stdout] 12 | #[typetag::serde(tag = "type")]
[INFO] [stdout]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    | |
[INFO] [stdout]    | `Strictest` is not local
[INFO] [stdout]    | move the `impl` block outside of this constant `_Backend_registry`
[INFO] [stdout] 13 | pub trait Backend: BackendClone + Display {
[INFO] [stdout]    |           ------- `Backend` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the attribute macro `typetag::serde` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the attribute macro `typetag::serde` may come from an old version of the `typetag_impl` crate, try updating your dependency with `cargo update -p typetag_impl`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the attribute macro `typetag::serde` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/repository/backend.rs:12:1
[INFO] [stdout]    |
[INFO] [stdout] 12 | #[typetag::serde(tag = "type")]
[INFO] [stdout]    | -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    | |
[INFO] [stdout]    | `Box` is not local
[INFO] [stdout]    | `Deserialize` is not local
[INFO] [stdout]    | move the `impl` block outside of this constant `_Backend_registry`
[INFO] [stdout] 13 | pub trait Backend: BackendClone + Display {
[INFO] [stdout]    |           ------- `Backend` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the attribute macro `typetag::serde` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the attribute macro `typetag::serde` may come from an old version of the `typetag_impl` crate, try updating your dependency with `cargo update -p typetag_impl`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the attribute macro `typetag::serde` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/repository/manager.rs:103:21
[INFO] [stdout]     |
[INFO] [stdout] 103 |     pub fn get_repo(&self, repo_name: impl AsRef<str>) -> SomaResult<Repository> {
[INFO] [stdout]     |                     ^^^^^ the lifetime is elided here                ^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 103 |     pub fn get_repo(&self, repo_name: impl AsRef<str>) -> SomaResult<Repository<'_>> {
[INFO] [stdout]     |                                                                                ++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]   --> tests/common/mod.rs:27:27
[INFO] [stdout]    |
[INFO] [stdout] 27 | pub fn test_env(data_dir: &mut DataDirectory) -> Environment<impl Connect, TestPrinter> {
[INFO] [stdout]    |                           ^^^^^^^^^^^^^^^^^^     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]    |                           |
[INFO] [stdout]    |                           the lifetime is elided here
[INFO] [stdout]    |
[INFO] [stdout]    = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout]    = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]    |
[INFO] [stdout] 27 | pub fn test_env(data_dir: &mut DataDirectory) -> Environment<'_, impl Connect, TestPrinter> {
[INFO] [stdout]    |                                                              +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]   --> tests/common/mod.rs:27:27
[INFO] [stdout]    |
[INFO] [stdout] 27 | pub fn test_env(data_dir: &mut DataDirectory) -> Environment<impl Connect, TestPrinter> {
[INFO] [stdout]    |                           ^^^^^^^^^^^^^^^^^^     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]    |                           |
[INFO] [stdout]    |                           the lifetime is elided here
[INFO] [stdout]    |
[INFO] [stdout]    = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout]    = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]    |
[INFO] [stdout] 27 | pub fn test_env(data_dir: &mut DataDirectory) -> Environment<'_, impl Connect, TestPrinter> {
[INFO] [stdout]    |                                                              +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]   --> src/bin/soma/main.rs:18:22
[INFO] [stdout]    |
[INFO] [stdout] 18 | fn cli_env(data_dir: &mut DataDirectory) -> SomaResult<Environment<impl Connect, TerminalPrinter>> {
[INFO] [stdout]    |                      ^^^^^^^^^^^^^^^^^^                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]    |                      |
[INFO] [stdout]    |                      the lifetime is elided here
[INFO] [stdout]    |
[INFO] [stdout]    = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout]    = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]    |
[INFO] [stdout] 18 | fn cli_env(data_dir: &mut DataDirectory) -> SomaResult<Environment<'_, impl Connect, TerminalPrinter>> {
[INFO] [stdout]    |                                                                    +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]   --> tests/common/mod.rs:27:27
[INFO] [stdout]    |
[INFO] [stdout] 27 | pub fn test_env(data_dir: &mut DataDirectory) -> Environment<impl Connect, TestPrinter> {
[INFO] [stdout]    |                           ^^^^^^^^^^^^^^^^^^     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]    |                           |
[INFO] [stdout]    |                           the lifetime is elided here
[INFO] [stdout]    |
[INFO] [stdout]    = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout]    = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]    |
[INFO] [stdout] 27 | pub fn test_env(data_dir: &mut DataDirectory) -> Environment<'_, impl Connect, TestPrinter> {
[INFO] [stdout]    |                                                              +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]   --> tests/common/mod.rs:27:27
[INFO] [stdout]    |
[INFO] [stdout] 27 | pub fn test_env(data_dir: &mut DataDirectory) -> Environment<impl Connect, TestPrinter> {
[INFO] [stdout]    |                           ^^^^^^^^^^^^^^^^^^     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]    |                           |
[INFO] [stdout]    |                           the lifetime is elided here
[INFO] [stdout]    |
[INFO] [stdout]    = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout]    = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]    |
[INFO] [stdout] 27 | pub fn test_env(data_dir: &mut DataDirectory) -> Environment<'_, impl Connect, TestPrinter> {
[INFO] [stdout]    |                                                              +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]   --> tests/common/mod.rs:27:27
[INFO] [stdout]    |
[INFO] [stdout] 27 | pub fn test_env(data_dir: &mut DataDirectory) -> Environment<impl Connect, TestPrinter> {
[INFO] [stdout]    |                           ^^^^^^^^^^^^^^^^^^     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]    |                           |
[INFO] [stdout]    |                           the lifetime is elided here
[INFO] [stdout]    |
[INFO] [stdout]    = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout]    = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]    |
[INFO] [stdout] 27 | pub fn test_env(data_dir: &mut DataDirectory) -> Environment<'_, impl Connect, TestPrinter> {
[INFO] [stdout]    |                                                              +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]   --> tests/common/mod.rs:27:27
[INFO] [stdout]    |
[INFO] [stdout] 27 | pub fn test_env(data_dir: &mut DataDirectory) -> Environment<impl Connect, TestPrinter> {
[INFO] [stdout]    |                           ^^^^^^^^^^^^^^^^^^     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]    |                           |
[INFO] [stdout]    |                           the lifetime is elided here
[INFO] [stdout]    |
[INFO] [stdout]    = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout]    = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]    |
[INFO] [stdout] 27 | pub fn test_env(data_dir: &mut DataDirectory) -> Environment<'_, impl Connect, TestPrinter> {
[INFO] [stdout]    |                                                              +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]   --> src/lib.rs:73:20
[INFO] [stdout]    |
[INFO] [stdout] 73 |     pub fn printer(&self) -> RefMut<P> {
[INFO] [stdout]    |                    ^^^^^     ^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]    |                    |
[INFO] [stdout]    |                    the lifetime is elided here
[INFO] [stdout]    |
[INFO] [stdout]    = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout]    = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]    |
[INFO] [stdout] 73 |     pub fn printer(&self) -> RefMut<'_, P> {
[INFO] [stdout]    |                                     +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]  --> src/error.rs:3:17
[INFO] [stdout]   |
[INFO] [stdout] 3 | #[derive(Debug, Fail)]
[INFO] [stdout]   |                 ^---
[INFO] [stdout]   |                 |
[INFO] [stdout]   |                 `Fail` is not local
[INFO] [stdout]   |                 move the `impl` block outside of this constant `_DERIVE_failure_Fail_FOR_Error`
[INFO] [stdout] 4 | pub enum Error {
[INFO] [stdout]   |          ----- `Error` is not local
[INFO] [stdout]   |
[INFO] [stdout]   = note: the derive macro `Fail` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]   = note: the derive macro `Fail` may come from an old version of the `failure_derive` crate, try updating your dependency with `cargo update -p failure_derive`
[INFO] [stdout]   = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]   = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]   = note: `#[warn(non_local_definitions)]` on by default
[INFO] [stdout]   = note: this warning originates in the derive macro `Fail` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]  --> src/error.rs:3:17
[INFO] [stdout]   |
[INFO] [stdout] 3 | #[derive(Debug, Fail)]
[INFO] [stdout]   |                 ^---
[INFO] [stdout]   |                 |
[INFO] [stdout]   |                 `Display` is not local
[INFO] [stdout]   |                 move the `impl` block outside of this constant `_DERIVE_failure_core_fmt_Display_FOR_Error`
[INFO] [stdout] 4 | pub enum Error {
[INFO] [stdout]   |          ----- `Error` is not local
[INFO] [stdout]   |
[INFO] [stdout]   = note: the derive macro `Fail` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]   = note: the derive macro `Fail` may come from an old version of the `failure_derive` crate, try updating your dependency with `cargo update -p failure_derive`
[INFO] [stdout]   = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]   = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]   = note: this warning originates in the derive macro `Fail` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]   --> src/repository.rs:77:20
[INFO] [stdout]    |
[INFO] [stdout] 77 |     pub fn manager(&self) -> &'a RepositoryManager {
[INFO] [stdout]    |                    ^^^^^         ^^^^^^^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]    |                    |
[INFO] [stdout]    |                    the lifetime is elided here
[INFO] [stdout]    |
[INFO] [stdout]    = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]    |
[INFO] [stdout] 77 |     pub fn manager(&self) -> &'a RepositoryManager<'_> {
[INFO] [stdout]    |                                                   ++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/repository/backend.rs:12:1
[INFO] [stdout]    |
[INFO] [stdout] 12 | #[typetag::serde(tag = "type")]
[INFO] [stdout]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    | |
[INFO] [stdout]    | `Serialize` is not local
[INFO] [stdout]    | move the `impl` block outside of this constant `_Backend_registry`
[INFO] [stdout] 13 | pub trait Backend: BackendClone + Display {
[INFO] [stdout]    |           ------- `Backend` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the attribute macro `typetag::serde` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the attribute macro `typetag::serde` may come from an old version of the `typetag_impl` crate, try updating your dependency with `cargo update -p typetag_impl`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the attribute macro `typetag::serde` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/repository/backend.rs:12:1
[INFO] [stdout]    |
[INFO] [stdout] 12 | #[typetag::serde(tag = "type")]
[INFO] [stdout]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    | |
[INFO] [stdout]    | `Send` is not local
[INFO] [stdout]    | `Serialize` is not local
[INFO] [stdout]    | move the `impl` block outside of this constant `_Backend_registry`
[INFO] [stdout] 13 | pub trait Backend: BackendClone + Display {
[INFO] [stdout]    |           ------- `Backend` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the attribute macro `typetag::serde` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the attribute macro `typetag::serde` may come from an old version of the `typetag_impl` crate, try updating your dependency with `cargo update -p typetag_impl`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the attribute macro `typetag::serde` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/repository/backend.rs:12:1
[INFO] [stdout]    |
[INFO] [stdout] 12 | #[typetag::serde(tag = "type")]
[INFO] [stdout]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    | |
[INFO] [stdout]    | `Sync` is not local
[INFO] [stdout]    | `Serialize` is not local
[INFO] [stdout]    | move the `impl` block outside of this constant `_Backend_registry`
[INFO] [stdout] 13 | pub trait Backend: BackendClone + Display {
[INFO] [stdout]    |           ------- `Backend` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the attribute macro `typetag::serde` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the attribute macro `typetag::serde` may come from an old version of the `typetag_impl` crate, try updating your dependency with `cargo update -p typetag_impl`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the attribute macro `typetag::serde` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/repository/backend.rs:12:1
[INFO] [stdout]    |
[INFO] [stdout] 12 | #[typetag::serde(tag = "type")]
[INFO] [stdout]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    | |
[INFO] [stdout]    | `Send` is not local
[INFO] [stdout]    | `Sync` is not local
[INFO] [stdout]    | `Serialize` is not local
[INFO] [stdout]    | move the `impl` block outside of this constant `_Backend_registry`
[INFO] [stdout] 13 | pub trait Backend: BackendClone + Display {
[INFO] [stdout]    |           ------- `Backend` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the attribute macro `typetag::serde` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the attribute macro `typetag::serde` may come from an old version of the `typetag_impl` crate, try updating your dependency with `cargo update -p typetag_impl`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the attribute macro `typetag::serde` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/repository/backend.rs:12:1
[INFO] [stdout]    |
[INFO] [stdout] 12 | #[typetag::serde(tag = "type")]
[INFO] [stdout]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ move the `impl` block outside of this constant `_Backend_registry`
[INFO] [stdout] 13 | pub trait Backend: BackendClone + Display {
[INFO] [stdout]    |           ------- `Backend` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the attribute macro `typetag::serde` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the attribute macro `typetag::serde` may come from an old version of the `typetag_impl` crate, try updating your dependency with `cargo update -p typetag_impl`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the attribute macro `typetag::serde` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/repository/backend.rs:12:1
[INFO] [stdout]    |
[INFO] [stdout] 12 | #[typetag::serde(tag = "type")]
[INFO] [stdout]    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    | |
[INFO] [stdout]    | `Strictest` is not local
[INFO] [stdout]    | move the `impl` block outside of this constant `_Backend_registry`
[INFO] [stdout] 13 | pub trait Backend: BackendClone + Display {
[INFO] [stdout]    |           ------- `Backend` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the attribute macro `typetag::serde` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the attribute macro `typetag::serde` may come from an old version of the `typetag_impl` crate, try updating your dependency with `cargo update -p typetag_impl`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the attribute macro `typetag::serde` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]   --> src/repository/backend.rs:12:1
[INFO] [stdout]    |
[INFO] [stdout] 12 | #[typetag::serde(tag = "type")]
[INFO] [stdout]    | -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    | |
[INFO] [stdout]    | `Box` is not local
[INFO] [stdout]    | `Deserialize` is not local
[INFO] [stdout]    | move the `impl` block outside of this constant `_Backend_registry`
[INFO] [stdout] 13 | pub trait Backend: BackendClone + Display {
[INFO] [stdout]    |           ------- `Backend` is not local
[INFO] [stdout]    |
[INFO] [stdout]    = note: the attribute macro `typetag::serde` defines the non-local `impl`, and may need to be changed
[INFO] [stdout]    = note: the attribute macro `typetag::serde` may come from an old version of the `typetag_impl` crate, try updating your dependency with `cargo update -p typetag_impl`
[INFO] [stdout]    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
[INFO] [stdout]    = note: this warning originates in the attribute macro `typetag::serde` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/repository/manager.rs:103:21
[INFO] [stdout]     |
[INFO] [stdout] 103 |     pub fn get_repo(&self, repo_name: impl AsRef<str>) -> SomaResult<Repository> {
[INFO] [stdout]     |                     ^^^^^ the lifetime is elided here                ^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]     |
[INFO] [stdout] 103 |     pub fn get_repo(&self, repo_name: impl AsRef<str>) -> SomaResult<Repository<'_>> {
[INFO] [stdout]     |                                                                                ++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]   --> src/bin/soma/main.rs:18:22
[INFO] [stdout]    |
[INFO] [stdout] 18 | fn cli_env(data_dir: &mut DataDirectory) -> SomaResult<Environment<impl Connect, TerminalPrinter>> {
[INFO] [stdout]    |                      ^^^^^^^^^^^^^^^^^^                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]    |                      |
[INFO] [stdout]    |                      the lifetime is elided here
[INFO] [stdout]    |
[INFO] [stdout]    = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout]    = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]    |
[INFO] [stdout] 18 | fn cli_env(data_dir: &mut DataDirectory) -> SomaResult<Environment<'_, impl Connect, TerminalPrinter>> {
[INFO] [stdout]    |                                                                    +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]     Finished `dev` profile [unoptimized + debuginfo] target(s) in 1m 01s
[INFO] [stderr] crater-edition-check: migrating to next edition
[INFO] [stderr]    Migrating Cargo.toml from 2018 edition to 2021
[INFO] [stderr] note: Switching to Edition 2021 will enable the use of the version 2 feature resolver in Cargo.
[INFO] [stderr] This may cause some dependencies to be built with fewer features enabled than previously.
[INFO] [stderr] More information about the resolver changes may be found at https://doc.rust-lang.org/nightly/edition-guide/rust-2021/default-cargo-resolver.html
[INFO] [stderr] When building the following dependencies, the given features will no longer be used:
[INFO] [stderr] 
[INFO] [stderr]   syn v2.0.118 (as host dependency) removed features: extra-traits, visit, visit-mut
[INFO] [stderr] 
[INFO] [stderr]     Checking soma-ctf v0.1.0-alpha (/opt/rustwide/workdir)
[INFO] [stderr]    Migrating src/lib.rs from 2021 edition to 2024
[INFO] [stderr]        Fixed src/repository/manager.rs (1 fix)
[INFO] [stdout] warning: `impl futures::Future<Item = Vec<SomaContainer>, Error = failure::Error>` will capture more lifetimes than possibly intended in edition 2024
[INFO] [stdout]    --> src/docker.rs:226:6
[INFO] [stdout]     |
[INFO] [stdout] 226 | ) -> impl Future<Item = Vec<SomaContainer>, Error = Error> {
[INFO] [stdout]     |      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout] note: specifically, these lifetimes are in scope but not mentioned in the type's bounds
[INFO] [stdout]    --> src/docker.rs:225:10
[INFO] [stdout]     |
[INFO] [stdout] 225 |     env: &Environment<impl Connect, impl Printer>,
[INFO] [stdout]     |          ^           ^
[INFO] [stdout]     = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024
[INFO] [stdout] note: you could use a `use<...>` bound to explicitly specify captures, but argument-position `impl Trait`s are not nameable
[INFO] [stdout]    --> src/docker.rs:225:23
[INFO] [stdout]     |
[INFO] [stdout] 225 |     env: &Environment<impl Connect, impl Printer>,
[INFO] [stdout]     |                       ^^^^^^^^^^^^  ^^^^^^^^^^^^
[INFO] [stdout]     = warning: this changes meaning in Rust 2024
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/rpit-lifetime-capture.html>
[INFO] [stdout]     = note: `--force-warn impl-trait-overcaptures` implied by `--force-warn rust-2024-compatibility`
[INFO] [stdout] help: use the precise capturing `use<...>` syntax to make the captures explicit
[INFO] [stdout]     |
[INFO] [stdout] 224 ~ pub fn list_containers<T: Connect, U: Printer>(
[INFO] [stdout] 225 ~     env: &Environment<T, U>,
[INFO] [stdout] 226 ~ ) -> impl Future<Item = Vec<SomaContainer>, Error = Error> + use<T, U> {
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: `impl futures::Future<Item = Vec<SomaImage>, Error = failure::Error>` will capture more lifetimes than possibly intended in edition 2024
[INFO] [stdout]    --> src/docker.rs:264:6
[INFO] [stdout]     |
[INFO] [stdout] 264 | ) -> impl Future<Item = Vec<SomaImage>, Error = Error> {
[INFO] [stdout]     |      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout] note: specifically, these lifetimes are in scope but not mentioned in the type's bounds
[INFO] [stdout]    --> src/docker.rs:263:10
[INFO] [stdout]     |
[INFO] [stdout] 263 |     env: &Environment<impl Connect, impl Printer>,
[INFO] [stdout]     |          ^           ^
[INFO] [stdout]     = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024
[INFO] [stdout] note: you could use a `use<...>` bound to explicitly specify captures, but argument-position `impl Trait`s are not nameable
[INFO] [stdout]    --> src/docker.rs:263:23
[INFO] [stdout]     |
[INFO] [stdout] 263 |     env: &Environment<impl Connect, impl Printer>,
[INFO] [stdout]     |                       ^^^^^^^^^^^^  ^^^^^^^^^^^^
[INFO] [stdout]     = warning: this changes meaning in Rust 2024
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/rpit-lifetime-capture.html>
[INFO] [stdout] help: use the precise capturing `use<...>` syntax to make the captures explicit
[INFO] [stdout]     |
[INFO] [stdout] 262 ~ pub fn list_images<T: Connect, U: Printer>(
[INFO] [stdout] 263 ~     env: &Environment<T, U>,
[INFO] [stdout] 264 ~ ) -> impl Future<Item = Vec<SomaImage>, Error = Error> + use<T, U> {
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: `impl futures::Future<Item = (), Error = failure::Error>` will capture more lifetimes than possibly intended in edition 2024
[INFO] [stdout]    --> src/docker.rs:385:6
[INFO] [stdout]     |
[INFO] [stdout] 385 | ) -> impl Future<Item = (), Error = Error> {
[INFO] [stdout]     |      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout] note: specifically, these lifetimes are in scope but not mentioned in the type's bounds
[INFO] [stdout]    --> src/docker.rs:383:10
[INFO] [stdout]     |
[INFO] [stdout] 383 |     env: &Environment<impl Connect, impl Printer>,
[INFO] [stdout]     |          ^           ^
[INFO] [stdout] 384 |     image_name: &str,
[INFO] [stdout]     |                 ^
[INFO] [stdout]     = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024
[INFO] [stdout] note: you could use a `use<...>` bound to explicitly specify captures, but argument-position `impl Trait`s are not nameable
[INFO] [stdout]    --> src/docker.rs:383:23
[INFO] [stdout]     |
[INFO] [stdout] 383 |     env: &Environment<impl Connect, impl Printer>,
[INFO] [stdout]     |                       ^^^^^^^^^^^^  ^^^^^^^^^^^^
[INFO] [stdout]     = warning: this changes meaning in Rust 2024
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/rpit-lifetime-capture.html>
[INFO] [stdout] help: use the precise capturing `use<...>` syntax to make the captures explicit
[INFO] [stdout]     |
[INFO] [stdout] 382 ~ pub fn remove_image<T: Connect, U: Printer>(
[INFO] [stdout] 383 ~     env: &Environment<T, U>,
[INFO] [stdout] 384 |     image_name: &str,
[INFO] [stdout] 385 ~ ) -> impl Future<Item = (), Error = Error> + use<T, U> {
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: `impl futures::Future<Item = (), Error = failure::Error>` will capture more lifetimes than possibly intended in edition 2024
[INFO] [stdout]    --> src/docker.rs:394:6
[INFO] [stdout]     |
[INFO] [stdout] 394 | ) -> impl Future<Item = (), Error = Error> {
[INFO] [stdout]     |      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout] note: specifically, these lifetimes are in scope but not mentioned in the type's bounds
[INFO] [stdout]    --> src/docker.rs:392:10
[INFO] [stdout]     |
[INFO] [stdout] 392 |     env: &Environment<impl Connect, impl Printer>,
[INFO] [stdout]     |          ^           ^
[INFO] [stdout] 393 |     container_id: &str,
[INFO] [stdout]     |                   ^
[INFO] [stdout]     = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024
[INFO] [stdout] note: you could use a `use<...>` bound to explicitly specify captures, but argument-position `impl Trait`s are not nameable
[INFO] [stdout]    --> src/docker.rs:392:23
[INFO] [stdout]     |
[INFO] [stdout] 392 |     env: &Environment<impl Connect, impl Printer>,
[INFO] [stdout]     |                       ^^^^^^^^^^^^  ^^^^^^^^^^^^
[INFO] [stdout]     = warning: this changes meaning in Rust 2024
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/rpit-lifetime-capture.html>
[INFO] [stdout] help: use the precise capturing `use<...>` syntax to make the captures explicit
[INFO] [stdout]     |
[INFO] [stdout] 391 ~ pub fn remove_container<T: Connect, U: Printer>(
[INFO] [stdout] 392 ~     env: &Environment<T, U>,
[INFO] [stdout] 393 |     container_id: &str,
[INFO] [stdout] 394 ~ ) -> impl Future<Item = (), Error = Error> + use<T, U> {
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: `impl futures::Future<Item = (), Error = failure::Error>` will capture more lifetimes than possibly intended in edition 2024
[INFO] [stdout]    --> src/docker.rs:402:6
[INFO] [stdout]     |
[INFO] [stdout] 402 | ) -> impl Future<Item = (), Error = Error> {
[INFO] [stdout]     |      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout] note: specifically, these lifetimes are in scope but not mentioned in the type's bounds
[INFO] [stdout]    --> src/docker.rs:400:10
[INFO] [stdout]     |
[INFO] [stdout] 400 |     env: &Environment<impl Connect, impl Printer>,
[INFO] [stdout]     |          ^           ^
[INFO] [stdout] 401 |     problem: &Problem,
[INFO] [stdout]     |              ^
[INFO] [stdout]     = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024
[INFO] [stdout] note: you could use a `use<...>` bound to explicitly specify captures, but argument-position `impl Trait`s are not nameable
[INFO] [stdout]    --> src/docker.rs:400:23
[INFO] [stdout]     |
[INFO] [stdout] 400 |     env: &Environment<impl Connect, impl Printer>,
[INFO] [stdout]     |                       ^^^^^^^^^^^^  ^^^^^^^^^^^^
[INFO] [stdout]     = warning: this changes meaning in Rust 2024
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/rpit-lifetime-capture.html>
[INFO] [stdout] help: use the precise capturing `use<...>` syntax to make the captures explicit
[INFO] [stdout]     |
[INFO] [stdout] 399 ~ pub fn prune_images_from_prob<T: Connect, U: Printer>(
[INFO] [stdout] 400 ~     env: &Environment<T, U>,
[INFO] [stdout] 401 |     problem: &Problem,
[INFO] [stdout] 402 ~ ) -> impl Future<Item = (), Error = Error> + use<T, U> {
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: `impl futures::Future<Item = (), Error = failure::Error>` will capture more lifetimes than possibly intended in edition 2024
[INFO] [stdout]    --> src/docker.rs:417:6
[INFO] [stdout]     |
[INFO] [stdout] 417 | ) -> impl Future<Item = (), Error = Error> {
[INFO] [stdout]     |      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout] note: specifically, these lifetimes are in scope but not mentioned in the type's bounds
[INFO] [stdout]    --> src/docker.rs:415:10
[INFO] [stdout]     |
[INFO] [stdout] 415 |     env: &Environment<impl Connect, impl Printer>,
[INFO] [stdout]     |          ^           ^
[INFO] [stdout] 416 |     problem: &Problem,
[INFO] [stdout]     |              ^
[INFO] [stdout]     = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024
[INFO] [stdout] note: you could use a `use<...>` bound to explicitly specify captures, but argument-position `impl Trait`s are not nameable
[INFO] [stdout]    --> src/docker.rs:415:23
[INFO] [stdout]     |
[INFO] [stdout] 415 |     env: &Environment<impl Connect, impl Printer>,
[INFO] [stdout]     |                       ^^^^^^^^^^^^  ^^^^^^^^^^^^
[INFO] [stdout]     = warning: this changes meaning in Rust 2024
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/rpit-lifetime-capture.html>
[INFO] [stdout] help: use the precise capturing `use<...>` syntax to make the captures explicit
[INFO] [stdout]     |
[INFO] [stdout] 414 ~ pub fn prune_containers_from_prob<T: Connect, U: Printer>(
[INFO] [stdout] 415 ~     env: &Environment<T, U>,
[INFO] [stdout] 416 |     problem: &Problem,
[INFO] [stdout] 417 ~ ) -> impl Future<Item = (), Error = Error> + use<T, U> {
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: `impl futures::Future<Item = (), Error = failure::Error>` will capture more lifetimes than possibly intended in edition 2024
[INFO] [stdout]    --> src/docker.rs:432:6
[INFO] [stdout]     |
[INFO] [stdout] 432 | ) -> impl Future<Item = (), Error = Error> {
[INFO] [stdout]     |      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout] note: specifically, these lifetimes are in scope but not mentioned in the type's bounds
[INFO] [stdout]    --> src/docker.rs:430:10
[INFO] [stdout]     |
[INFO] [stdout] 430 |     env: &Environment<impl Connect, impl Printer>,
[INFO] [stdout]     |          ^           ^
[INFO] [stdout] 431 |     container_id: &str,
[INFO] [stdout]     |                   ^
[INFO] [stdout]     = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024
[INFO] [stdout] note: you could use a `use<...>` bound to explicitly specify captures, but argument-position `impl Trait`s are not nameable
[INFO] [stdout]    --> src/docker.rs:430:23
[INFO] [stdout]     |
[INFO] [stdout] 430 |     env: &Environment<impl Connect, impl Printer>,
[INFO] [stdout]     |                       ^^^^^^^^^^^^  ^^^^^^^^^^^^
[INFO] [stdout]     = warning: this changes meaning in Rust 2024
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/rpit-lifetime-capture.html>
[INFO] [stdout] help: use the precise capturing `use<...>` syntax to make the captures explicit
[INFO] [stdout]     |
[INFO] [stdout] 429 ~ pub fn start<T: Connect, U: Printer>(
[INFO] [stdout] 430 ~     env: &Environment<T, U>,
[INFO] [stdout] 431 |     container_id: &str,
[INFO] [stdout] 432 ~ ) -> impl Future<Item = (), Error = Error> + use<T, U> {
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: `impl futures::Future<Item = (), Error = failure::Error>` will capture more lifetimes than possibly intended in edition 2024
[INFO] [stdout]    --> src/docker.rs:440:6
[INFO] [stdout]     |
[INFO] [stdout] 440 | ) -> impl Future<Item = (), Error = Error> {
[INFO] [stdout]     |      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout] note: specifically, these lifetimes are in scope but not mentioned in the type's bounds
[INFO] [stdout]    --> src/docker.rs:438:10
[INFO] [stdout]     |
[INFO] [stdout] 438 |     env: &Environment<impl Connect, impl Printer>,
[INFO] [stdout]     |          ^           ^
[INFO] [stdout] 439 |     container_id: &str,
[INFO] [stdout]     |                   ^
[INFO] [stdout]     = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024
[INFO] [stdout] note: you could use a `use<...>` bound to explicitly specify captures, but argument-position `impl Trait`s are not nameable
[INFO] [stdout]    --> src/docker.rs:438:23
[INFO] [stdout]     |
[INFO] [stdout] 438 |     env: &Environment<impl Connect, impl Printer>,
[INFO] [stdout]     |                       ^^^^^^^^^^^^  ^^^^^^^^^^^^
[INFO] [stdout]     = warning: this changes meaning in Rust 2024
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/rpit-lifetime-capture.html>
[INFO] [stdout] help: use the precise capturing `use<...>` syntax to make the captures explicit
[INFO] [stdout]     |
[INFO] [stdout] 437 ~ pub fn stop<T: Connect, U: Printer>(
[INFO] [stdout] 438 ~     env: &Environment<T, U>,
[INFO] [stdout] 439 |     container_id: &str,
[INFO] [stdout] 440 ~ ) -> impl Future<Item = (), Error = Error> + use<T, U> {
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: `impl futures::Future<Item = Vec<SomaContainer>, Error = failure::Error>` will capture more lifetimes than possibly intended in edition 2024
[INFO] [stdout]    --> src/docker.rs:226:6
[INFO] [stdout]     |
[INFO] [stdout] 226 | ) -> impl Future<Item = Vec<SomaContainer>, Error = Error> {
[INFO] [stdout]     |      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout] note: specifically, these lifetimes are in scope but not mentioned in the type's bounds
[INFO] [stdout]    --> src/docker.rs:225:10
[INFO] [stdout]     |
[INFO] [stdout] 225 |     env: &Environment<impl Connect, impl Printer>,
[INFO] [stdout]     |          ^           ^
[INFO] [stdout]     = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024
[INFO] [stdout] note: you could use a `use<...>` bound to explicitly specify captures, but argument-position `impl Trait`s are not nameable
[INFO] [stdout]    --> src/docker.rs:225:23
[INFO] [stdout]     |
[INFO] [stdout] 225 |     env: &Environment<impl Connect, impl Printer>,
[INFO] [stdout]     |                       ^^^^^^^^^^^^  ^^^^^^^^^^^^
[INFO] [stdout]     = warning: this changes meaning in Rust 2024
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/rpit-lifetime-capture.html>
[INFO] [stdout]     = note: `--force-warn impl-trait-overcaptures` implied by `--force-warn rust-2024-compatibility`
[INFO] [stdout] help: use the precise capturing `use<...>` syntax to make the captures explicit
[INFO] [stdout]     |
[INFO] [stdout] 224 ~ pub fn list_containers<T: Connect, U: Printer>(
[INFO] [stdout] 225 ~     env: &Environment<T, U>,
[INFO] [stdout] 226 ~ ) -> impl Future<Item = Vec<SomaContainer>, Error = Error> + use<T, U> {
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: `impl futures::Future<Item = Vec<SomaImage>, Error = failure::Error>` will capture more lifetimes than possibly intended in edition 2024
[INFO] [stdout]    --> src/docker.rs:264:6
[INFO] [stdout]     |
[INFO] [stdout] 264 | ) -> impl Future<Item = Vec<SomaImage>, Error = Error> {
[INFO] [stdout]     |      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout] note: specifically, these lifetimes are in scope but not mentioned in the type's bounds
[INFO] [stdout]    --> src/docker.rs:263:10
[INFO] [stdout]     |
[INFO] [stdout] 263 |     env: &Environment<impl Connect, impl Printer>,
[INFO] [stdout]     |          ^           ^
[INFO] [stdout]     = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024
[INFO] [stdout] note: you could use a `use<...>` bound to explicitly specify captures, but argument-position `impl Trait`s are not nameable
[INFO] [stdout]    --> src/docker.rs:263:23
[INFO] [stdout]     |
[INFO] [stdout] 263 |     env: &Environment<impl Connect, impl Printer>,
[INFO] [stdout]     |                       ^^^^^^^^^^^^  ^^^^^^^^^^^^
[INFO] [stdout]     = warning: this changes meaning in Rust 2024
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/rpit-lifetime-capture.html>
[INFO] [stdout] help: use the precise capturing `use<...>` syntax to make the captures explicit
[INFO] [stdout]     |
[INFO] [stdout] 262 ~ pub fn list_images<T: Connect, U: Printer>(
[INFO] [stdout] 263 ~     env: &Environment<T, U>,
[INFO] [stdout] 264 ~ ) -> impl Future<Item = Vec<SomaImage>, Error = Error> + use<T, U> {
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: `impl futures::Future<Item = (), Error = failure::Error>` will capture more lifetimes than possibly intended in edition 2024
[INFO] [stdout]    --> src/docker.rs:385:6
[INFO] [stdout]     |
[INFO] [stdout] 385 | ) -> impl Future<Item = (), Error = Error> {
[INFO] [stdout]     |      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout] note: specifically, these lifetimes are in scope but not mentioned in the type's bounds
[INFO] [stdout]    --> src/docker.rs:383:10
[INFO] [stdout]     |
[INFO] [stdout] 383 |     env: &Environment<impl Connect, impl Printer>,
[INFO] [stdout]     |          ^           ^
[INFO] [stdout] 384 |     image_name: &str,
[INFO] [stdout]     |                 ^
[INFO] [stdout]     = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024
[INFO] [stdout] note: you could use a `use<...>` bound to explicitly specify captures, but argument-position `impl Trait`s are not nameable
[INFO] [stdout]    --> src/docker.rs:383:23
[INFO] [stdout]     |
[INFO] [stdout] 383 |     env: &Environment<impl Connect, impl Printer>,
[INFO] [stdout]     |                       ^^^^^^^^^^^^  ^^^^^^^^^^^^
[INFO] [stdout]     = warning: this changes meaning in Rust 2024
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/rpit-lifetime-capture.html>
[INFO] [stdout] help: use the precise capturing `use<...>` syntax to make the captures explicit
[INFO] [stdout]     |
[INFO] [stdout] 382 ~ pub fn remove_image<T: Connect, U: Printer>(
[INFO] [stdout] 383 ~     env: &Environment<T, U>,
[INFO] [stdout] 384 |     image_name: &str,
[INFO] [stdout] 385 ~ ) -> impl Future<Item = (), Error = Error> + use<T, U> {
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: `impl futures::Future<Item = (), Error = failure::Error>` will capture more lifetimes than possibly intended in edition 2024
[INFO] [stdout]    --> src/docker.rs:394:6
[INFO] [stdout]     |
[INFO] [stdout] 394 | ) -> impl Future<Item = (), Error = Error> {
[INFO] [stdout]     |      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout] note: specifically, these lifetimes are in scope but not mentioned in the type's bounds
[INFO] [stdout]    --> src/docker.rs:392:10
[INFO] [stdout]     |
[INFO] [stdout] 392 |     env: &Environment<impl Connect, impl Printer>,
[INFO] [stdout]     |          ^           ^
[INFO] [stdout] 393 |     container_id: &str,
[INFO] [stdout]     |                   ^
[INFO] [stdout]     = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024
[INFO] [stdout] note: you could use a `use<...>` bound to explicitly specify captures, but argument-position `impl Trait`s are not nameable
[INFO] [stdout]    --> src/docker.rs:392:23
[INFO] [stdout]     |
[INFO] [stdout] 392 |     env: &Environment<impl Connect, impl Printer>,
[INFO] [stdout]     |                       ^^^^^^^^^^^^  ^^^^^^^^^^^^
[INFO] [stdout]     = warning: this changes meaning in Rust 2024
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/rpit-lifetime-capture.html>
[INFO] [stdout] help: use the precise capturing `use<...>` syntax to make the captures explicit
[INFO] [stdout]     |
[INFO] [stdout] 391 ~ pub fn remove_container<T: Connect, U: Printer>(
[INFO] [stdout] 392 ~     env: &Environment<T, U>,
[INFO] [stdout] 393 |     container_id: &str,
[INFO] [stdout] 394 ~ ) -> impl Future<Item = (), Error = Error> + use<T, U> {
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: `impl futures::Future<Item = (), Error = failure::Error>` will capture more lifetimes than possibly intended in edition 2024
[INFO] [stdout]    --> src/docker.rs:402:6
[INFO] [stdout]     |
[INFO] [stdout] 402 | ) -> impl Future<Item = (), Error = Error> {
[INFO] [stdout]     |      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout] note: specifically, these lifetimes are in scope but not mentioned in the type's bounds
[INFO] [stdout]    --> src/docker.rs:400:10
[INFO] [stdout]     |
[INFO] [stdout] 400 |     env: &Environment<impl Connect, impl Printer>,
[INFO] [stdout]     |          ^           ^
[INFO] [stdout] 401 |     problem: &Problem,
[INFO] [stdout]     |              ^
[INFO] [stdout]     = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024
[INFO] [stdout] note: you could use a `use<...>` bound to explicitly specify captures, but argument-position `impl Trait`s are not nameable
[INFO] [stdout]    --> src/docker.rs:400:23
[INFO] [stdout]     |
[INFO] [stdout] 400 |     env: &Environment<impl Connect, impl Printer>,
[INFO] [stdout]     |                       ^^^^^^^^^^^^  ^^^^^^^^^^^^
[INFO] [stdout]     = warning: this changes meaning in Rust 2024
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/rpit-lifetime-capture.html>
[INFO] [stdout] help: use the precise capturing `use<...>` syntax to make the captures explicit
[INFO] [stdout]     |
[INFO] [stdout] 399 ~ pub fn prune_images_from_prob<T: Connect, U: Printer>(
[INFO] [stdout] 400 ~     env: &Environment<T, U>,
[INFO] [stdout] 401 |     problem: &Problem,
[INFO] [stdout] 402 ~ ) -> impl Future<Item = (), Error = Error> + use<T, U> {
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: `impl futures::Future<Item = (), Error = failure::Error>` will capture more lifetimes than possibly intended in edition 2024
[INFO] [stdout]    --> src/docker.rs:417:6
[INFO] [stdout]     |
[INFO] [stdout] 417 | ) -> impl Future<Item = (), Error = Error> {
[INFO] [stdout]     |      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout] note: specifically, these lifetimes are in scope but not mentioned in the type's bounds
[INFO] [stdout]    --> src/docker.rs:415:10
[INFO] [stdout]     |
[INFO] [stdout] 415 |     env: &Environment<impl Connect, impl Printer>,
[INFO] [stdout]     |          ^           ^
[INFO] [stdout] 416 |     problem: &Problem,
[INFO] [stdout]     |              ^
[INFO] [stdout]     = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024
[INFO] [stdout] note: you could use a `use<...>` bound to explicitly specify captures, but argument-position `impl Trait`s are not nameable
[INFO] [stdout]    --> src/docker.rs:415:23
[INFO] [stdout]     |
[INFO] [stdout] 415 |     env: &Environment<impl Connect, impl Printer>,
[INFO] [stdout]     |                       ^^^^^^^^^^^^  ^^^^^^^^^^^^
[INFO] [stdout]     = warning: this changes meaning in Rust 2024
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/rpit-lifetime-capture.html>
[INFO] [stdout] help: use the precise capturing `use<...>` syntax to make the captures explicit
[INFO] [stdout]     |
[INFO] [stdout] 414 ~ pub fn prune_containers_from_prob<T: Connect, U: Printer>(
[INFO] [stdout] 415 ~     env: &Environment<T, U>,
[INFO] [stdout] 416 |     problem: &Problem,
[INFO] [stdout] 417 ~ ) -> impl Future<Item = (), Error = Error> + use<T, U> {
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: `impl futures::Future<Item = (), Error = failure::Error>` will capture more lifetimes than possibly intended in edition 2024
[INFO] [stdout]    --> src/docker.rs:432:6
[INFO] [stdout]     |
[INFO] [stdout] 432 | ) -> impl Future<Item = (), Error = Error> {
[INFO] [stdout]     |      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout] note: specifically, these lifetimes are in scope but not mentioned in the type's bounds
[INFO] [stdout]    --> src/docker.rs:430:10
[INFO] [stdout]     |
[INFO] [stdout] 430 |     env: &Environment<impl Connect, impl Printer>,
[INFO] [stdout]     |          ^           ^
[INFO] [stdout] 431 |     container_id: &str,
[INFO] [stdout]     |                   ^
[INFO] [stdout]     = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024
[INFO] [stdout] note: you could use a `use<...>` bound to explicitly specify captures, but argument-position `impl Trait`s are not nameable
[INFO] [stdout]    --> src/docker.rs:430:23
[INFO] [stdout]     |
[INFO] [stdout] 430 |     env: &Environment<impl Connect, impl Printer>,
[INFO] [stdout]     |                       ^^^^^^^^^^^^  ^^^^^^^^^^^^
[INFO] [stdout]     = warning: this changes meaning in Rust 2024
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/rpit-lifetime-capture.html>
[INFO] [stdout] help: use the precise capturing `use<...>` syntax to make the captures explicit
[INFO] [stdout]     |
[INFO] [stdout] 429 ~ pub fn start<T: Connect, U: Printer>(
[INFO] [stdout] 430 ~     env: &Environment<T, U>,
[INFO] [stdout] 431 |     container_id: &str,
[INFO] [stdout] 432 ~ ) -> impl Future<Item = (), Error = Error> + use<T, U> {
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: `impl futures::Future<Item = (), Error = failure::Error>` will capture more lifetimes than possibly intended in edition 2024
[INFO] [stdout]    --> src/docker.rs:440:6
[INFO] [stdout]     |
[INFO] [stdout] 440 | ) -> impl Future<Item = (), Error = Error> {
[INFO] [stdout]     |      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout] note: specifically, these lifetimes are in scope but not mentioned in the type's bounds
[INFO] [stdout]    --> src/docker.rs:438:10
[INFO] [stdout]     |
[INFO] [stdout] 438 |     env: &Environment<impl Connect, impl Printer>,
[INFO] [stdout]     |          ^           ^
[INFO] [stdout] 439 |     container_id: &str,
[INFO] [stdout]     |                   ^
[INFO] [stdout]     = note: all lifetimes in scope will be captured by `impl Trait`s in edition 2024
[INFO] [stdout] note: you could use a `use<...>` bound to explicitly specify captures, but argument-position `impl Trait`s are not nameable
[INFO] [stdout]    --> src/docker.rs:438:23
[INFO] [stdout]     |
[INFO] [stdout] 438 |     env: &Environment<impl Connect, impl Printer>,
[INFO] [stdout]     |                       ^^^^^^^^^^^^  ^^^^^^^^^^^^
[INFO] [stdout]     = warning: this changes meaning in Rust 2024
[INFO] [stdout]     = note: for more information, see <https://doc.rust-lang.org/edition-guide/rust-2024/rpit-lifetime-capture.html>
[INFO] [stdout] help: use the precise capturing `use<...>` syntax to make the captures explicit
[INFO] [stdout]     |
[INFO] [stdout] 437 ~ pub fn stop<T: Connect, U: Printer>(
[INFO] [stdout] 438 ~     env: &Environment<T, U>,
[INFO] [stdout] 439 |     container_id: &str,
[INFO] [stdout] 440 ~ ) -> impl Future<Item = (), Error = Error> + use<T, U> {
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]    Migrating tests/build_clean.rs from 2021 edition to 2024
[INFO] [stderr]        Fixed tests/common/mod.rs (1 fix)
[INFO] [stderr]    Migrating tests/update.rs from 2021 edition to 2024
[INFO] [stderr]    Migrating tests/fetch.rs from 2021 edition to 2024
[INFO] [stderr]    Migrating tests/add_remove.rs from 2021 edition to 2024
[INFO] [stderr]    Migrating tests/location_to_backend.rs from 2021 edition to 2024
[INFO] [stderr]    Migrating tests/run_stop.rs from 2021 edition to 2024
[INFO] [stderr]    Migrating src/bin/soma/main.rs from 2021 edition to 2024
[INFO] [stderr]        Fixed src/bin/soma/main.rs (1 fix)
[INFO] [stderr]     Finished `dev` profile [unoptimized + debuginfo] target(s) in 1m 06s
[INFO] [stderr] crater-edition-check: soma-ctf v0.1.0-alpha (/opt/rustwide/workdir) updating edition from 2021 to 2024
[INFO] [stderr]     Checking soma-ctf v0.1.0-alpha (/opt/rustwide/workdir)
[INFO] [stdout] error[E0515]: cannot return value referencing function parameter `container_name`
[INFO] [stdout]    --> src/ops.rs:177:13
[INFO] [stdout]     |
[INFO] [stdout] 177 |             docker::start(env, &container_name).map(|_| container_name)
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^---------------^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |             |                  |
[INFO] [stdout]     |             |                  `container_name` is borrowed here
[INFO] [stdout]     |             returns a value referencing data owned by the current function
[INFO] [stdout]     |
[INFO] [stdout] note: this call may capture more lifetimes than intended, because Rust 2024 has adjusted the `impl Trait` lifetime capture rules
[INFO] [stdout]    --> src/ops.rs:177:13
[INFO] [stdout]     |
[INFO] [stdout] 177 |             docker::start(env, &container_name).map(|_| container_name)
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] note: you could use a `use<...>` bound to explicitly specify captures, but argument-position `impl Trait`s are not nameable
[INFO] [stdout]    --> src/docker.rs:430:23
[INFO] [stdout]     |
[INFO] [stdout] 430 |     env: &Environment<impl Connect, impl Printer>,
[INFO] [stdout]     |                       ^^^^^^^^^^^^  ^^^^^^^^^^^^
[INFO] [stdout] help: use the precise capturing `use<...>` syntax to make the captures explicit
[INFO] [stdout]    --> src/docker.rs:429:13
[INFO] [stdout]     |
[INFO] [stdout] 429 ~ pub fn start<T: Connect, U: Printer>(
[INFO] [stdout] 430 ~     env: &Environment<T, U>,
[INFO] [stdout] 431 |     container_id: &str,
[INFO] [stdout] 432 ~ ) -> impl Future<Item = (), Error = Error> + use<T, U> {
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0505]: cannot move out of `container_name` because it is borrowed
[INFO] [stdout]    --> src/ops.rs:177:53
[INFO] [stdout]     |
[INFO] [stdout] 175 |         docker::create(env, labels, &image_name, port_str).and_then(|container_name| {
[INFO] [stdout]     |                                                                      --------------- return type of closure `futures::future::Map<impl futures::Future<Item = (), Error = failure::Error>, {closure@src/ops.rs:177:53: 177:56}>` contains a lifetime `'1`
[INFO] [stdout]     |                                                                      |
[INFO] [stdout]     |                                                                      binding `container_name` declared here
[INFO] [stdout] 176 |             env.printer().write_line("Starting container...");
[INFO] [stdout] 177 |             docker::start(env, &container_name).map(|_| container_name)
[INFO] [stdout]     |             ----------------------------------------^^^----------------
[INFO] [stdout]     |             |                  |                    |   |
[INFO] [stdout]     |             |                  |                    |   move occurs due to use in closure
[INFO] [stdout]     |             |                  |                    move out of `container_name` occurs here
[INFO] [stdout]     |             |                  borrow of `container_name` occurs here
[INFO] [stdout]     |             returning this value requires that `container_name` is borrowed for `'1`
[INFO] [stdout]     |
[INFO] [stdout] note: this call may capture more lifetimes than intended, because Rust 2024 has adjusted the `impl Trait` lifetime capture rules
[INFO] [stdout]    --> src/ops.rs:177:13
[INFO] [stdout]     |
[INFO] [stdout] 177 |             docker::start(env, &container_name).map(|_| container_name)
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] note: you could use a `use<...>` bound to explicitly specify captures, but argument-position `impl Trait`s are not nameable
[INFO] [stdout]    --> src/docker.rs:430:23
[INFO] [stdout]     |
[INFO] [stdout] 430 |     env: &Environment<impl Connect, impl Printer>,
[INFO] [stdout]     |                       ^^^^^^^^^^^^  ^^^^^^^^^^^^
[INFO] [stdout] help: use the precise capturing `use<...>` syntax to make the captures explicit
[INFO] [stdout]    --> src/docker.rs:429:13
[INFO] [stdout]     |
[INFO] [stdout] 429 ~ pub fn start<T: Connect, U: Printer>(
[INFO] [stdout] 430 ~     env: &Environment<T, U>,
[INFO] [stdout] 431 |     container_id: &str,
[INFO] [stdout] 432 ~ ) -> impl Future<Item = (), Error = Error> + use<T, U> {
[INFO] [stdout]     |
[INFO] [stdout] help: consider cloning the value if the performance cost is acceptable
[INFO] [stdout]     |
[INFO] [stdout] 177 |             docker::start(env, &container_name.clone()).map(|_| container_name)
[INFO] [stdout]     |                                               ++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0515]: cannot return value referencing function parameter `container_name`
[INFO] [stdout]    --> src/ops.rs:177:13
[INFO] [stdout]     |
[INFO] [stdout] 177 |             docker::start(env, &container_name).map(|_| container_name)
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^---------------^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |             |                  |
[INFO] [stdout]     |             |                  `container_name` is borrowed here
[INFO] [stdout]     |             returns a value referencing data owned by the current function
[INFO] [stdout]     |
[INFO] [stdout] note: this call may capture more lifetimes than intended, because Rust 2024 has adjusted the `impl Trait` lifetime capture rules
[INFO] [stdout]    --> src/ops.rs:177:13
[INFO] [stdout]     |
[INFO] [stdout] 177 |             docker::start(env, &container_name).map(|_| container_name)
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] note: you could use a `use<...>` bound to explicitly specify captures, but argument-position `impl Trait`s are not nameable
[INFO] [stdout]    --> src/docker.rs:430:23
[INFO] [stdout]     |
[INFO] [stdout] 430 |     env: &Environment<impl Connect, impl Printer>,
[INFO] [stdout]     |                       ^^^^^^^^^^^^  ^^^^^^^^^^^^
[INFO] [stdout] help: use the precise capturing `use<...>` syntax to make the captures explicit
[INFO] [stdout]    --> src/docker.rs:429:13
[INFO] [stdout]     |
[INFO] [stdout] 429 ~ pub fn start<T: Connect, U: Printer>(
[INFO] [stdout] 430 ~     env: &Environment<T, U>,
[INFO] [stdout] 431 |     container_id: &str,
[INFO] [stdout] 432 ~ ) -> impl Future<Item = (), Error = Error> + use<T, U> {
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0505]: cannot move out of `container_name` because it is borrowed
[INFO] [stdout]    --> src/ops.rs:177:53
[INFO] [stdout]     |
[INFO] [stdout] 175 |         docker::create(env, labels, &image_name, port_str).and_then(|container_name| {
[INFO] [stdout]     |                                                                      --------------- return type of closure `futures::future::Map<impl futures::Future<Item = (), Error = failure::Error>, {closure@src/ops.rs:177:53: 177:56}>` contains a lifetime `'1`
[INFO] [stdout]     |                                                                      |
[INFO] [stdout]     |                                                                      binding `container_name` declared here
[INFO] [stdout] 176 |             env.printer().write_line("Starting container...");
[INFO] [stdout] 177 |             docker::start(env, &container_name).map(|_| container_name)
[INFO] [stdout]     |             ----------------------------------------^^^----------------
[INFO] [stdout]     |             |                  |                    |   |
[INFO] [stdout]     |             |                  |                    |   move occurs due to use in closure
[INFO] [stdout]     |             |                  |                    move out of `container_name` occurs here
[INFO] [stdout]     |             |                  borrow of `container_name` occurs here
[INFO] [stdout]     |             returning this value requires that `container_name` is borrowed for `'1`
[INFO] [stdout]     |
[INFO] [stdout] note: this call may capture more lifetimes than intended, because Rust 2024 has adjusted the `impl Trait` lifetime capture rules
[INFO] [stdout]    --> src/ops.rs:177:13
[INFO] [stdout]     |
[INFO] [stdout] 177 |             docker::start(env, &container_name).map(|_| container_name)
[INFO] [stdout]     |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout] note: you could use a `use<...>` bound to explicitly specify captures, but argument-position `impl Trait`s are not nameable
[INFO] [stdout]    --> src/docker.rs:430:23
[INFO] [stdout]     |
[INFO] [stdout] 430 |     env: &Environment<impl Connect, impl Printer>,
[INFO] [stdout]     |                       ^^^^^^^^^^^^  ^^^^^^^^^^^^
[INFO] [stdout] help: use the precise capturing `use<...>` syntax to make the captures explicit
[INFO] [stdout]    --> src/docker.rs:429:13
[INFO] [stdout]     |
[INFO] [stdout] 429 ~ pub fn start<T: Connect, U: Printer>(
[INFO] [stdout] 430 ~     env: &Environment<T, U>,
[INFO] [stdout] 431 |     container_id: &str,
[INFO] [stdout] 432 ~ ) -> impl Future<Item = (), Error = Error> + use<T, U> {
[INFO] [stdout]     |
[INFO] [stdout] help: consider cloning the value if the performance cost is acceptable
[INFO] [stdout]     |
[INFO] [stdout] 177 |             docker::start(env, &container_name.clone()).map(|_| container_name)
[INFO] [stdout]     |                                               ++++++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] Some errors have detailed explanations: E0505, E0515.
[INFO] [stdout] 
[INFO] [stdout] For more information about an error, try `rustc --explain E0505`.
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `soma-ctf` (lib) due to 2 previous errors
[INFO] [stderr] warning: build failed, waiting for other jobs to finish...
[INFO] [stdout] Some errors have detailed explanations: E0505, E0515.
[INFO] [stdout] 
[INFO] [stdout] For more information about an error, try `rustc --explain E0505`.
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `soma-ctf` (lib test) due to 2 previous errors
[INFO] running `Command { std: "docker" "inspect" "d39ec109b3c5270d1d929f84117aff0ae0af8cb60e1318da9824fd07448c723c", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "d39ec109b3c5270d1d929f84117aff0ae0af8cb60e1318da9824fd07448c723c", kill_on_drop: false }`
[INFO] [stdout] d39ec109b3c5270d1d929f84117aff0ae0af8cb60e1318da9824fd07448c723c
